All updates

Product 14 July 2026 4 min read

Dune in your editor

A native extension for VS Code and a command-line client. It reads the repository, proposes the change, and runs the tests.

Until now, using Dune for code meant copying files into a conversation and copying the answer back out. That worked, but it made Dune a consultant rather than a colleague. Today it moves in. The VS Code extension and the dune command-line client are available to everyone on Pro and above.

How it works

Open a project and ask for a change in plain language. Dune reads the files it needs — it is good at finding them — and writes back a proposed diff, one file at a time, with a sentence explaining each edit. You accept, reject or amend every hunk. Nothing lands until you say so.

If the project has tests, Dune runs them after the change and reads the output. When something fails it fixes its own work before it hands the change back, and it tells you what it tried. We watched a lot of these loops during the beta; the most common outcome is that the second attempt passes and the first attempt's mistake is explained in one line.

The terminal

The command-line client does the same job without a window. dune "make the date parser accept ISO week numbers" works in any repository, streams the reasoning to the terminal, and opens the diff in your pager. It is what our own team uses most.

It is the first tool that argues back. I bring it a plan and it finds the assumption I was hoping nobody would notice.

Privacy

Your code is sent to Dune only for the request you make and is not retained afterwards. On Team and Enterprise plans it is never used to train models. The extension shows you the exact files it read on every turn, so there is never a question of what left the machine.